-These notes are compiled from xen-devel questions and postings that have occured
+These notes are compiled from xen-devel questions and postings that have occurred
since the inclusion of XSM. These notes are not intended to be definitive
documentation but should address many common problems that arrise when
experimenting with XSM:FLASK.
vcpu_schedule_unlock_irq(v);
irqlocked = 0;
- printk("Terminal machine check exception occured in "
+ printk("Terminal machine check exception occurred in "
"hypervisor context.\n");
/* If MCG_STATUS_EIPV indicates, the IP on the stack is related
mc_global->mc_coreid, mc_global->mc_gstatus);
} else {
printk(XENLOG_WARNING "MCE: The hardware reports a non "
- "fatal, correctable incident occured on "
+ "fatal, correctable incident occurred on "
"CPU %d.\n",
mc_global->mc_coreid);
}
addl $((6+4)*4),%esi
# %gs:%esi now points to the guest stack before the
- # interrupt/exception occured.
+ # interrupt/exception occurred.
movl $PER_CPU_GDT_ENTRY*8,%ecx
lsll %ecx,%ecx
unsigned long ip; /* where did the overflow interrupt happened */
unsigned long tstamp; /* ar.itc when entering perfmon intr. handler */
- unsigned short cpu; /* cpu on which the overfow occured */
+ unsigned short cpu; /* cpu on which the overfow occurred */
unsigned short set; /* event set active when overflow ocurred */
int tgid; /* thread group id (for NPTL, this is getpid()) */
} pfm_default_smpl_entry_t;
/* rr7 (and rr6) may already be set to XEN_EFI_RR7 (and XEN_EFI_RR6), which
* would indicate a nested EFI, SAL or PAL call, such
- * as from an MCA. This may have occured during a call
+ * as from an MCA. This may have occurred during a call
* to set_one_rr_efi(). To be safe, repin everything anyway.
*/